either continue loading sites or make certain notification to restart
Categories
(Core :: General, defect)
Tracking
()
People
(Reporter: dchmelik, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0
Steps to reproduce:
One thing I noticed in recent years is FireFox stops loading sites but only then if you open a new tab will it say you're forced to restart because of an upgrade. Mainly I think this is very bad because it sometimes interrupts important activities/work, rather than the historically normal (and better) practice of letting the user decide if/when to upgrade and if/when to restart.
Actual results:
OS upgraded FireFox. Stopped being able to load sites and got zero notification until opening a new tab. Sometimes needed to continue doing things before restarting.
Expected results:
Let users decide if/when to restart, because they may be doing things that shouldn't be interrupted. Make certain they always get the notification without having to open a new tab.
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Reporter | ||
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Hi :mossop, I am wondering if "Toolkit:: Startup and Profile System" a better fit for this behavior change ticket. If not, do you have ideas for the right component? Thank you.
Updated•1 year ago
|
Reporter | ||
Comment 4•1 year ago
|
||
Since only my OS updates FireFox (FireFox can't itself) this isn't duplicate of bug 1480452.
This typically happens after FireFox finished starting (even hours later) so I don't think has anything to do with startup, and I wouldn't really say this has to do with profiles or most/any components, as I described two related things FireFox does or doesn't and what it should (immediately notify users there's been an upgrade without waiting for a new tab, and don't say/force 'restart to continue using FireFox' rather than let users continue using).
If you're still following the horrible fad of cloning Chrome, note when I upgrade my Chrome package I can still use chrome as long as I want... it never forces restart: that's entirely up to me, and just uses the new version after I decide to exit. As such, I can use Chrome for certain work/jobs/positions but FireFox isn't 'production-ready' for work/jobs/positions you can't have browsing interrupted.
Comment 5•1 year ago
|
||
Basically the same issue as bug 1705217
Comment 6•1 year ago
|
||
This should be mitigated by using our deb package
Description
•